Mac Expert 1995 Winter/Mac Expert - Winter 95.iso/Les fichiers/Utilitaires divers/Anti - virus/Disinfectant 3.6/Disinfectant 3.6.rsrc/STR#_230.txt

Text File | 1995-04-07 | 12.1 KB | 631 lines







3



3





åError Messages





This section presents all of Disinfectant’s error messages, in alphabetical

order, with a brief explanation of each one.





### An error or inconsistency was detected while

### trying to repair this file.

### WARNING: This file may still be infected!



Your file was infected, but while attempting to repair it, Disinfectant

discovered something wrong with the file. The file may still be infected.

Scan the file again with Disinfectant to find out if it is still infected. If it

is still infected, you should delete it. If Disinfectant reports that it is no

longer infected, you can try running it to see if it works. It may be usable

or it may be damaged in such a way that it cannot be used. This error is

not common, but it can occur in unusual situations.





One situation in which this error can occur is if an application is infected

by more than one virus and you attempt to use some other virus tool to

repair the file before running Disinfectant. Some other virus tools cannot

handle multiple infections properly and they sometimes leave the

application damaged in such a way that Disinfectant cannot repair it

properly.





### An I/O error occurred while trying to check

### this file.



### An I/O error occurred while trying to repair

### this file.

### WARNING: This file may still be infected!



These error messages are listed in the report if a hardware error occurs

while trying to read or write a file. They usually mean that the disk itself

or the disk drive is not operating properly. You can try running

Disinfectant again on the same file. If the hardware problem is

intermittent, it might work the second time.







### File infected by xxxxx.



Your file is infected by a virus. “xxxxx” is the name of the virus

(Scores, nVIR A, etc.).







### File infected by an unknown strain of xxxx



Your file is infected by a strain of the WDEF or CDEF virus which has not

yet been reported. If you have not already repaired the file, we would

appreciate it if you would send us a copy of the infected file. See the

sections on the WDEF and CDEF viruses for more information.







### File partially infected by xxxxx,

### but not contagious.



Your file is partially infected by the virus named “xxxxx,” but the

infection is not contagious. These kinds of infections are not dangerous and

they cannot spread to other files. You may choose to leave the infection in

the file or you may use Disinfectant to remove the infection.



Partially infected files sometimes are the result of other virus tools

which have errors. The other virus tool may remove part of an infection,

but not all of the infection.



Partial infections can also arise on Gatekeeper-protected systems. In

particular, if the Scores virus attacks a Gatekeeper-protected system, a

harmless part of the Scores infection will manage to evade Gatekeeper’s

protection mechanisms.







### File partially infected by nVIR A or nVIR B,

### but not contagious.



nVIR A and nVIR B are different viruses, but some of their parts are

identical. It is possible for only these common parts to be present in an

infected file. In this case, Disinfectant has no way of knowing which virus

originally attacked the file, so it issues this special message.







### NOTE: Some errors were reported. For a detailed

### explanation of an error message, press Command-?

### and click the error message text.



This message appears in the summary section of the report if any other

error messages occurred during a scan.







### Scan canceled.



You canceled a scan or disinfection run.







### System files cannot be scanned over TOPS.



This error should only occur if you try to scan a disk over a TOPS

network. TOPS does not permit access to currently active System files

over the network. We recommend that you scan the disk using the Mac to

which the disk is directly connected.



If this error occurs in some other situation, it means that there is

probably an error in Disinfectant. We would appreciate it if you would

send a report to the author.







### The disk is too full to repair this file.

### WARNING: This file may still be infected!



This error may occur if a disk is very full and you attempt to repair an

infected file on the disk. Disinfectant requires at least a small amount of

free space on the disk before it can repair the file. Try moving some of

the files on the disk to some other disk to make more room and run

Disinfectant again.







### The inserted disk is uninitialized, damaged,

### or not a Mac disk. It cannot be scanned.



This error occurs if you insert an uninitialized, damaged, or

non-Macintosh disk on a scanning station with no mouse or keyboard. The

disk is ejected and not scanned.







### The resource fork of this file is damaged or

### in an unknown format. It cannot be checked.



Macintosh files have two parts or “forks:” the resource fork and the

data fork. When Disinfectant checks a file, it tries to open the resource

fork. This message means that the information stored in the resource fork

is not valid resource information. The data fork may still be intact and

usable. For document files, this is usually not a problem. For applications

and system files, this usually indicates that something is seriously wrong

with the file and you should replace it with a known good copy of the file.





WARNING: It is possible for an application to be damaged and yet still be

infected and contagious. For this reason, you should not attempt to use

applications which have damaged resource forks.



For some reason, we have seen invalid resource information in a number

of StuffIt archive files. These “damaged” files are usually still usable

since StuffIt stores the archived files in the data fork, not the resource

fork.



Disinfectant also reports that all Reflex database files are “damaged.”

Reflex makes non-standard use of the resource fork in its database files.

These files are not really damaged. They are still usable, but only by

Reflex.



The same problem has been reported with some files created by MacTran,

which also makes non-standard use of the resource fork.



The same problem has also been reported with the “phrase library” files

created by Studio Session and Super Studio Session.





### There is not enough memory to check this file.



### There is not enough memory to repair this file.

### WARNING: This file is probably still infected!



Disinfectant was unable to get enough memory to check or repair the file.



This error is usually caused by applications which contain very large

CODE resources. Disinfectant must load these resources into memory to

check them for viruses and, if there is not enough memory available, you

get this error message.



Another possible cause of this error is that the file is damaged.



If you get this error, you should give Disinfectant more memory. Quit

Disinfectant. Select the Disinfectant program icon in the Finder. Select the

Finder’s “Get Info” command in the “File” menu. Increase the amount of

memory allocated to Disinfectant in the Get Info window. Close the Get

Info window. Run Disinfectant again.







### This file is busy and cannot be checked.



Your file could not be opened for reading because the file was already open

with exclusive access by some other application. This message should

only occur on server disks. For server disks, we recommend that you

remove the server from production and restart using a startup floppy

disk. This should avoid file busy errors. For more details on scanning

servers, see the “Special Features” section.







### This file is busy and cannot be repaired.

### Restart using a locked Apple “Disk Tools”

### disk and try running Disinfectant again.

### WARNING: This file is still infected!



### This file is busy and cannot be repaired.

### Restart using your locked “Virus Tools”

### disk and try running Disinfectant again.

### WARNING: This file is still infected!



### This file is busy and cannot be repaired.

### To repair this file, rebuild the desktop.

### WARNING: This file is still infected!



Your file could not be opened for writing because the file was already open

by some other application. This error is common when using System 7,

System 6 with MultiFinder, or when scanning server disks. For server

disks, we recommend that you remove the server from production and

restart it using a locked startup floppy. This should avoid file busy

errors. For more details on scanning servers, see the “Special Features”

section.



The first message above is only issued under System 7. The second

message above is only issued under System 6.



The third message above is issued when a Finder desktop file is infected

and busy. In this case, the easiest way to remove the infection is to

rebuild the desktop. See the “Problem Clinic” section for details.







### This file was damaged by the virus, and it cannot

### be repaired properly. You should delete the file

### and replace it with a known good copy.



Viruses sometimes damage files in such a way that they cannot be

repaired properly. In this case, Disinfectant removes the virus from the

file, but leaves the file damaged. You should not attempt to use such a file.

You should delete it and replace it with a known good copy of the file.





In particular, the T4 virus damages files when it infects them. Files

infected by T4 cannot be repaired. If you attempt to repair a file infected

by T4, you will get this error message. See the section on T4 for details.



This error message is also issued when the Scores virus has infected a

System file from Apple’s System Software release 6.0.4 or later. See

the section on Scores for details.



The MDEF D virus can also sometimes damage applications. See the section

on MDEF for details.





### Unexpected error (nnn).



### Unexpected error (nnn) occurred while trying

### to open this file for repair.

### WARNING: This file is still infected!



Unexpected errors should not occur. It means that there may be an error

in Disinfectant. We would appreciate it if you would send a note to the

author describing what you were doing when the error occurred. Please

specify the error number reported in the message. If possible, also send

us a copy of the file that was being scanned when the error occurred.







### Unexpected error (nnn). If you are using

### Gatekeeper, check to make certain you have

### granted privileges to Disinfectant.

### WARNING: This file is probably still infected!



One possible cause of unexpected errors is attempting to repair infected

files on a Gatekeeper-protected system when you have forgotten to grant

Disinfectant privileges. You should grant Disinfectant all privileges

(“File” and “Res” privileges for “Other,” “System” and “Self”).







### WARNING: You do not have the proper privileges

### to access files in some of the folders. Some

### files in those folders may be infected!



### You do not have Make Changes privilege

### to the folder containing this file.

### It cannot be repaired.

### WARNING: This file is still infected!



### You do not have See Files privilege

### to this folder. Files within this folder

### cannot be checked.





### You do not have See Folders privilege

### to this folder. Folders within this folder

### cannot be checked.



### You have neither See Files nor See Folders

### privileges to this folder. This folder

### cannot be checked.



These error messages are issued if a server folder is encountered for

which you do not have the necessary access privileges. To avoid these

errors, we recommend that you remove the server from production and

restart it using a locked startup floppy. For more details on scanning

servers, see the “Special Features” section.